Repository navigation
feat: open app links like slack:// in the service they belong to - #2598
Open
eXistenZNL wants to merge 3 commits into
Open
eXistenZNL wants to merge 3 commits into
eXistenZNL wants to merge 3 commits into
Conversation
This was referenced Oct 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pre-flight Checklist
Please ensure you've completed all of the following.
Description of Change
This PR lets Ferdium open the app links of a service, like the
slack://link behind the "Open in app" button on a Slack web page, and lets each recipe decide which links are its own.scheme://link it is launched with, except its ownferdium://deep links.resolveLink(link, context)method. Ferdium asks the recipe of each displayed service, in sidebar order, whether a link is its own; the recipe returns the URL its service should load, ornull. The base class returnsnull, so existing recipes keep working. When no recipe claims an http(s) link, Ferdium falls back to the same host matching as in feat: open http(s) links in the service they belong to #2597.webview.jscan store details the page knows and Ferdium doesn't withFerdium.setLinkContext({ ... }). Ferdium saves them with the service, only when they change, and passes them toresolveLink. Slack uses this to recognize which workspace aslack://link is meant for.config.protocols, for example["slack"].xdg-mime. The setting is hidden on macOS, where an app can only handle the protocols listed in itsInfo.plistat build time; that will be a separate PR.docs/OPENING_LINKS.mddescribes how a link travels through Ferdium and what a recipe can do.This builds on #2597, so this PR also contains its commits until #2595 and #2597 are merged.
Part of a Larger Feature
This PR is part of a larger feature: letting Ferdium open links in the service they belong to, so it behaves more like the native apps of those services. That covers web links (for example a Slack permalink handed to Ferdium by a link router) and the app links of a service (for example the
slack://link behind the "Open in app" button on a Slack web page). Each recipe decides which links are its own, so a service can add support for its links without changes to Ferdium itself. App links can be enabled on Linux and Windows; macOS will follow in a later PR.The feature is split up so each part can be reviewed on its own:
Motivation and Context
Ferdium handles a ton of services for me; with this change it can behave much more like the various native apps that exist for each service. Having this feature makes the whole process of getting a link into Ferdium (where you are logged in to a service) much more integrated.
Checklist
pnpm prepare-code)pnpm testpassesRelease Notes
New setting to let Ferdium open the app links of your services, like slack://.